High-level function-organization description {software architecture} {system architecture} defines system.
Components include applications, technical services, integration services, business services, and data services {computer system}.
Architectures {Common Object Request Broker Architecture} can have object-oriented ways to handle data between clients and servers, using Interface Definition Language (IDL) and Internet Inter-ORB Protocol (CORBA).
execution environment {envelope, computing}.
Models {implementation model} can describe function logical and physical representation.
Modules can have use in several programs {overlaying}.
User-interface sections {punch-out} can be for multiple applications.
Method invocations {Remote Method Invocations} (RMI) can use Java data model.
Related reusable class sets {toolkit} provide general functions.
Integrated project stages, methods, and principles {unified process} develop and maintain software.
Objects {value object} transfer data between presentation and domain layers.
Tools {software design tools} can check high-level design models {model checking}, using automated reasoning on structure language, to prove algorithms have no counterexamples or contradictions. Integrated-circuit design uses model checking. Systems have object operations, mappings, and relations, with assertions. Design-checkers try to find cases in which assertions are not true, so designers can exclude those cases.
Designs {contract-based design} can specify contracts between user and service provider. If user provides requisites {pre-conditions}, then service provider guarantees service will perform functions and give results {post-conditions}.
Starting with requirements, specifying functions and designing objects {responsibility-driven design} can meet requirements.
Designs {top-down design} can use modules, which contain submodules, which contain sub-submodules, and so on.
Abstract-class sets {framework} can work together in reusable designs.
Frameworks {request-response framework} can be integration services that send service requests to technical services, applications, and business-model instances and receive responses. Service-request {request, computer} execution environment can include required input. Service-response {response, computer} execution environment can include output.
Frameworks {services framework} can define and specify service uses.
System components {software layers} can be for applications, technical services, integration services, business services, and data services.
Software layers {application layer} can include installers and user interfaces and use business and technical services, through integration services. Interfaces are for navigating, querying, calculating, displaying, and reporting.
Software layers {business layer} can include instrument controls, analysis tools, quality-control modules, parameter settings, queries, and business objects. Models {business model} can be business-object content, behavior, rules, and interactions. Data objects {business object} are in systems. Service groups {business service} access and control shared domain-specific service interfaces, such as instrument controls and data.
Software layers {data layer} can include auditing, ID, password, authentication, persistence, and relational database. Implementation-model subset {data model} describes persistent procedure, trigger, and constraint logical and physical data representation.
Software layers {domain layer} can contain modules working with data objects. Business-model subsets {domain model} can have business types.
Software layers {integration layer} can include request-response, instrument, workflow, directory, and messaging services. A service group {integration service} includes request-response framework, architectural framework, and services that access and control shared services.
Software layers {presentation layer} can contain user interfaces.
Querying, versioning, or persisting data {system service} {software services} happens upon request for service or system function. Software components {service provider} provide service functions, such as for instrument runtime or messaging. System-architecture primary services allow other-service development.
Java class and component-library APIs {Java Database Connectivity} (JDBC) can allow Java applications to communicate with database server, outside database software.
Services {Java Message Service} (JMS) can publish and listen for messages.
Java extensions {Java Naming and Directory Interface} (JNDI) can provide API for accessing directory and naming services, such as LDAP, Novell Netware NDS, CORBA Naming Service, and naming services provided by EJB servers. EJB servers organize beans into directory structure and provide JNDI driver service provider for accessing directory structure.
JNDI database {naming service} contains named objects, with no attributes.
Infrastructure services {technical service} can be for applications and business services: logging, security, exceptions, and system management.
3-Computer Science-Software-Programming
Outline of Knowledge Database Home Page
Description of Outline of Knowledge Database
Date Modified: 2022.0225